Breadth-first search 방식의 Problem solving .
“
A breadth first problem solving approach requries someone with the expertise to understand how the details will most likely emerge and the savvy to know when the time to make commitments has arrived. Howevery, the breadth first approach does not need a stable domain; it is the approach of choice when the business domain is expected to evolve. It is also an effective approach when the domain is stable. —p60, Lean software development (book) , Chapter 3 “Decide as late as possible ” 중
목차
See also
Depth-first problem solving 목차 관련 글 Integrated problem solving “Product development is a system of interconnected problem-solving cycles, and frequent problem-solving cycles t…” 이터레이션 “Second, short Iterations are an options-based approach to software development.” Amplify learning “Second, short iterations are an options-based approach to software development.” Build integrity in 관련 절: [[Lean software development]]의 원칙 중 하나. Set-based development 관련 절: [[Lean software development]] 전문성 관련 절: [[Lean software development]] Making decisions ‘최대한 늦게 결정’를 함께 참조 Think aloud 관련 절: Think-Aloud Problem Solving (TAPS) 최대한 빠른 인도 “The principle "deliver as fast as possible" complements Decide as late as possible.” 옵션 기반 사고 관련 절: [[Lean software development]] 소프트웨어 테스팅의 교훈들 “If the problem isn't solved, the product doesn't work.” Pull system “There are two ways to assure that workers make the most effective use of their time.” Wastes of software development “Minimizing partially done software development is a risk-reduction as well as a waste-reduction strategy.” Self determination 관련 절: [[Lean software development]] Introduction to machine learning problem framing “Determining whether ML is the right approach for solving a problem.” Conceptual integrity 주제어가 겹침 전체를 보기 “Quite often, the common good suffers if people attend first to their own specialized interests.” Simple rule “Thus, simple rules are a key mechanism to enable people to Decide as late as possible. --p65” 큐잉 이론 “Thus, with iterative development, it is critically important that you do not have a bottleneck at testing. --p79” Last responsible moment 관련 절: [[Lean software development]]